Designing for the User Experience in Learning Systems by Evangelos Kapros & Maria Koutsombogera

Author:Evangelos Kapros & Maria Koutsombogera
Language: eng
Format: epub
ISBN: 9783319947945
Publisher: Springer International Publishing

6.5 Drafting User Experience Questionnaires

Traditionally, user interaction with persons with disabilities requested for the user to tick if they were: blind or low sighted or deaf and hard of hearing. Some even went as far as asking the % of disability in their condition. While offering important information regarding their condition, other more important traits were overseen, for example, if a person is a fast reader. After many tests across Europe (Romero-Fresco 2015), it was found that reading subtitles was not related to any condition, but to reading ability, usually related to education. Consequently, we feel it is high time to take into consideration a new approach when designing the steps of a process aiming at offering any e-learning product taking user needs and requirements into account.

As we have already seen, under Sen’s approach, disability can be understood as a deprivation in terms of capabilities or functionings that results from the interaction of an individual’s (a) personal characteristics (age, impairment, etc.) and (b) available goods (assets, income) and (c) environment (social, economic, political, cultural) (Mitra 2006). This is to say that disability means lacking certain capabilities/functionings due to the combination of the above-mentioned factors. Consequently, when working with users to design any content, platform or technology for e-learning two issues need to be considered: (a) their capabilities and functionings (where they are and where they want to be) and (b) their personal characteristics, commodities and environment.

To design the methodology of any project aiming at producing e-learning materials for all citizens we suggest the following steps. 1.First of all gather a small group of people representing end user capabilities to collect information regarding expectations and needs. This stage is basic also to understand the validation process. The users in this first interaction can be called “super users” since, besides their condition of regular users, they also have some knowledge on the items to be tested. It would make no sense to consult users with no knowledge or experience with neither functional diversity nor technological background since at this stage what we require is not their acceptance of the final service, but system requirements.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.